home *** CD-ROM | disk | FTP | other *** search
rrrroooobbbbooooiiiinnnnsssstttt____ccccoooonnnnffffiiiigggg((((1111MMMM)))) rrrroooobbbbooooiiiinnnnsssstttt____ccccoooonnnnffffiiiigggg((((1111MMMM)))) NNNNAAAAMMMMEEEE roboinst_config, mrconfig - configure automatic installation server directory SSSSYYYYNNNNOOOOPPPPSSSSIIIISSSS rrrroooobbbbooooiiiinnnnsssstttt____ccccoooonnnnffffiiiigggg [ ----nnnnxxxxyyyy ] [ ----cccc configdir ] DDDDEEEESSSSCCCCRRRRIIIIPPPPTTTTIIIIOOOONNNN _r_o_b_o_i_n_s_t__c_o_n_f_i_g is run on the configuration server system to check and index the contents of an _r_o_b_o_i_n_s_t configuration directory (ccccoooonnnnffffiiiiggggddddiiiirrrr). The _m_r_c_o_n_f_i_g file is parsed for errors, other scripts, if any, are checked, and a table of contents is built. Any custom configuration directories (for specific hardware or network addresses) beneath the configuration directory are also checked and included in the table of contents. _r_o_b_o_i_n_s_t__c_o_n_f_i_g first reads the _m_r_c_o_n_f_i_g file. The _m_r_c_o_n_f_i_g file must be present in the configuration directory. The _m_r_c_o_n_f_i_g file controls the RoboInst automatic installation session. Each line in the _m_r_c_o_n_f_i_g file is a statement which specifies actions to occur at each phase of the automatic installation. Each statement is comprised of a _k_e_y_w_o_r_d and its arguments. The ordering of lines is only significant among lines that have the same _k_e_y_w_o_r_d. For example, all lines that begin with the iiiinnnnsssstttt _k_e_y_w_o_r_d are assumed to contain input lines for _i_n_s_t(1M), and this input is passed to _i_n_s_t in the same order it appears in the _m_r_c_o_n_f_i_g file. Blank lines and lines beginning with #### are ignored. This is the order in which events happen in an automatic installation process in the miniroot: 1111.... system restarted to the miniroot 2222.... configuration directory downloaded and _m_r_c_o_n_f_i_g file preprocessed 3333.... iiiinnnniiiitttt keyword commands executed 4444.... disks partitioned as per ppppaaaarrrrttttiiiittttiiiioooonnnn keywords 5555.... ffffxxxx keyword commands executed 6666.... filesystems created as per ppppaaaarrrrttttiiiittttiiiioooonnnn keywords 7777.... mmmmkkkkffffssss keyword commands executed 8888.... filesystems mounted 9999.... pppprrrreeeeiiiinnnnsssstttt keyword commands executed 11110000.... iiiinnnnsssstttt keyword commands executed 11111111.... build new kernel, unless the nnnnooookkkkeeeerrrrnnnneeeellll keyword is specified 11112222.... ppppoooossssttttiiiinnnnsssstttt keyword commands executed 11113333.... restart system to multi-user mode In a live automatic installation the order of events is as follows: PPPPaaaaggggeeee 1111 rrrroooobbbbooooiiiinnnnsssstttt____ccccoooonnnnffffiiiigggg((((1111MMMM)))) rrrroooobbbbooooiiiinnnnsssstttt____ccccoooonnnnffffiiiigggg((((1111MMMM)))) 1111.... configuration directory downloaded and _m_r_c_o_n_f_i_g file preprocessed 2222.... iiiinnnniiiitttt keyword commands executed 3333.... pppprrrreeeeiiiinnnnsssstttt keyword commands executed 4444.... iiiinnnnsssstttt keyword commands executed 5555.... ppppoooossssttttiiiinnnnsssstttt keyword commands executed The syntax of the _m_r_c_o_n_f_i_g keywords is detailed below: vvvveeeerrrrssssiiiioooonnnn _n_u_m_b_e_r Versioning information in case new keywords are added in the future. If this keyword is omitted, version 1 is assumed. The RoboInst software will terminate with an error if it encounters a _m_r_c_o_n_f_i_g file with a higher version number. lllloooogggghhhhoooosssstttt _I_P _a_d_d_r_e_s_s(_e_s) The IP address(es) of the host(s) to which syslog messages will be forwarded, in addition to being logged on the client. sssseeeetttteeeennnnvvvv _v_a_r_i_a_b_l_e _v_a_l_u_e Set the named RoboInst environment variable. The variable is also exported to subcommands, such as those executed in the pppprrrreeeeiiiinnnnsssstttt, ppppoooossssttttiiiinnnnsssstttt, etc., phases of the installation. oooonnnneeeerrrrrrrroooorrrr _a_c_t_i_o_n The oooonnnneeeerrrrrrrroooorrrr keyword controls the behavior of _i_n_s_t in response to an error, such as incompatible product selections, disk space shortages, etc. If set to iiiiggggnnnnoooorrrreeee, the default, then _i_n_s_t continues without stopping if an error is detected (errors are still reported in /_r_o_o_t/_v_a_r/_i_n_s_t/_I_N_S_T_L_O_G and in the SYSLOG). If set to wwwwaaaaiiiitttt, _i_n_s_t will stop and wait for a response from the user (interactive mode) whenever an error occurs. ppppaaaarrrrttttiiiittttiiiioooonnnn _d_e_v_i_c_e _s_i_z_e _t_y_p_e _n_a_m_e _o_p_t_i_o_n_s Specify partitions to create and filesystems to mount (see PPPPaaaarrrrttttiiiittttiiiioooonnnniiiinnnngggg section below). ddddiiiisssskkkksssseeeettttuuuupppp This keyword is required when repartitioning of the root disk drive is requested, and the drive is either uninitialized (has no volume header) or in a pre-6.5 format, that is, when swap is not located just after the volume header at the physical beginning of the drive. Specifying this keyword will cause the swap partition to be relocated to the beginning of the drive, when the installation session is initiated from multi- user mode using _r_o_b_o_i_n_s_t(1M). NNNNooootttteeee:::: if the installation is initiated from the PROM command monitor, the ddddiiiisssskkkksssseeeettttuuuupppp keyword will be ignored. You must also specify ddddiiiisssskkkksssseeeettttuuuupppp====ttttrrrruuuueeee on the bbbbooooooootttt command line when initiating roboinst from the PROM command monitor (see _p_r_o_m(1M)). See PPPPaaaarrrrttttiiiittttiiiioooonnnniiiinnnngggg section below. PPPPaaaaggggeeee 2222 rrrroooobbbbooooiiiinnnnsssstttt____ccccoooonnnnffffiiiigggg((((1111MMMM)))) rrrroooobbbbooooiiiinnnnsssstttt____ccccoooonnnnffffiiiigggg((((1111MMMM)))) iiiinnnniiiitttt /_b_i_n/_s_h _c_o_m_m_a_n_d This keyword is used to specify shell commands to be executed during the iiiinnnniiiitttt phase. ffffxxxx /_b_i_n/_s_h _c_o_m_m_a_n_d This keyword is used to specify shell commands to be executed during the ffffxxxx phase. mmmmkkkkffffssss /_b_i_n/_s_h _c_o_m_m_a_n_d This keyword is used to specify shell commands to be executed during the mmmmkkkkffffssss phase. pppprrrreeeeiiiinnnnsssstttt /_b_i_n/_s_h _c_o_m_m_a_n_d This keyword is used to specify shell commands to be executed during the pppprrrreeeeiiiinnnnsssstttt phase. iiiinnnnsssstttt _i_n_s_t _c_o_m_m_a_n_d _I_n_s_t command to be executed. Multiple iiiinnnnsssstttt keywords may be specified. Commands are collected in the order they appear in the _m_r_c_o_n_f_i_g file, copied into a temporary command file, and _i_n_s_t is invoked with the ----cccc argument. nnnnooookkkkeeeerrrrnnnneeeellll The presence of this keyword causes the _a_u_t_o_c_o_n_f_i_g(1M) phase to be skipped, so that a new UNIX kernel will not be automatically generated. If you use this keyword, you must manually build the UNIX kernel from your own scripts, if necessary. Normally a new kernel named /_r_o_o_t/_u_n_i_x._i_n_s_t_a_l_l is generated by the _a_u_t_o_c_o_n_f_i_g(1M) command. If it builds successfully, it is renamed to /_r_o_o_t/_u_n_i_x before the system is restarted to multi-user mode, something like this: _iiii_ffff _eeee_cccc_hhhh_oooo _yyyy _|||| _cccc_hhhh_rrrr_oooo_oooo_tttt _////_rrrr_oooo_oooo_tttt _\\\\ _////_eeee_tttt_cccc_////_iiii_nnnn_iiii_tttt_...._dddd_////_aaaa_uuuu_tttt_oooo_cccc_oooo_nnnn_ffff_iiii_gggg _----_oooo _----_NNNN _tttt_hhhh_eeee_nnnn _mmmm_vvvv _////_rrrr_oooo_oooo_tttt_////_uuuu_nnnn_iiii_xxxx_...._iiii_nnnn_ssss_tttt_aaaa_llll_llll _////_rrrr_oooo_oooo_tttt_////_uuuu_nnnn_iiii_xxxx _ffff_iiii ppppoooossssttttiiiinnnnsssstttt /_b_i_n/_s_h _c_o_m_m_a_n_d This keyword is used to specify shell commands to be executed during the ppppoooossssttttiiiinnnnsssstttt phase. iiiiffff /_b_i_n/_s_h _c_o_m_m_a_n_d ............ eeeellllssssiiiiffff /_b_i_n/_s_h _c_o_m_m_a_n_d ............ eeeellllsssseeee ............ eeeennnnddddiiiiffff The conditional syntax is similar to the iiiiffff syntax in _s_h(1). The first command is executed and if it exits with a status of zero, then all lines up to the next eeeellllsssseeee, eeeellllssssiiiiffff or eeeennnnddddiiiiffff PPPPaaaaggggeeee 3333 rrrroooobbbbooooiiiinnnnsssstttt____ccccoooonnnnffffiiiigggg((((1111MMMM)))) rrrroooobbbbooooiiiinnnnsssstttt____ccccoooonnnnffffiiiigggg((((1111MMMM)))) statement are evaluated. Otherwise, the next command is executed and if its exit status is zero, all lines up to the next eeeellllsssseeee, eeeellllssssiiiiffff or eeeennnnddddiiiiffff statement are evaluated, and so on. If all the commands exit non-zero, lines following the final eeeellllsssseeee (if present) are evaluated. As in /bin/sh, the eeeellllssssiiiiffff and eeeellllsssseeee clauses are optional. Multiple eeeellllssssiiiiffff clauses are allowed. Nesting of iiiiffff statements is permitted. Any trailing ;;;; tttthhhheeeennnn is stripped from iiiiffff and eeeellllssssiiiiffff statements before the command is executed. Conditional statements are useful for performing different disk partitioning, or software installation instructions, depending on CPU or graphics type, for example: if [ $SGI_CPUBOARD = IP30 ]; then init echo This is an Octane elsif [ $SGI_CPUBOARD = IP22 ]; then init echo This is an Indy else init echo Neither an Octane nor an Indy endif EEEEnnnnvvvviiiirrrroooonnnnmmmmeeeennnntttt VVVVaaaarrrriiiiaaaabbbblllleeeessss RoboInst exports environment variables to commands and subcommands executed during the automatic installation. Some variables can have multiple values. In that case the values are separated by whitespace. The pre-defined variables and values are as follows: SSSSGGGGIIII____CCCCPPPPUUUUBBBBOOOOAAAARRRRDDDD The value of CPUBOARD as per the _i_n_s_t(1M) aaaaddddmmmmiiiinnnn hhhhaaaarrrrddddwwwwaaaarrrreeee command. SSSSGGGGIIII____CCCCPPPPUUUUAAAARRRRCCCCHHHH SSSSGGGGIIII____AAAABBBBIIII SSSSGGGGIIII____CCCCPPPPUUUUAAAARRRRCCCCHHHH is set to the value of CPUARCH as per the _i_n_s_t(1M) aaaaddddmmmmiiiinnnn hhhhaaaarrrrddddwwwwaaaarrrreeee command, specifically, the processor type. The value of the CPUARCH _A_B_I(5) type is available in the SSSSGGGGIIII____AAAABBBBIIII variable. For example, if _i_n_s_t reports both CPUARCH=R4000 and CPUARCH=MIPS2, then the variable SSSSGGGGIIII____CCCCPPPPUUUUAAAARRRRCCCCHHHH is set to R4000, and SSSSGGGGIIII____AAAABBBBIIII is set to MIPS2. SSSSGGGGIIII____GGGGFFFFXXXXBBBBOOOOAAAARRRRDDDD The value of GFXBOARD as per the _i_n_s_t(1M) aaaaddddmmmmiiiinnnn hhhhaaaarrrrddddwwwwaaaarrrreeee command. SSSSGGGGIIII____SSSSUUUUBBBBGGGGRRRR The value of SUBGR as per the _i_n_s_t(1M) aaaaddddmmmmiiiinnnn hhhhaaaarrrrddddwwwwaaaarrrreeee command. PPPPaaaaggggeeee 4444 rrrroooobbbbooooiiiinnnnsssstttt____ccccoooonnnnffffiiiigggg((((1111MMMM)))) rrrroooobbbbooooiiiinnnnsssstttt____ccccoooonnnnffffiiiigggg((((1111MMMM)))) SSSSGGGGIIII____MMMMOOOODDDDEEEE The value of MODE as per the _i_n_s_t(1M) aaaaddddmmmmiiiinnnn hhhhaaaarrrrddddwwwwaaaarrrreeee command. SSSSGGGGIIII____MMMMAAAACCCCHHHHIIIINNNNEEEE The value of MACHINE as per the _i_n_s_t(1M) aaaaddddmmmmiiiinnnn hhhhaaaarrrrddddwwwwaaaarrrreeee command. SSSSGGGGIIII____IIIIPPPPAAAADDDDDDDDRRRR The network IP address of the system, as stored in the _n_v_r_a_m(1M) nnnneeeettttaaaaddddddddrrrr variable. SSSSGGGGIIII____CCCCAAAAPPPPAAAACCCCIIIITTTTYYYY SSSSGGGGIIII____CCCCAAAAPPPP____ddddkkkkssss####dddd####vvvvoooollll SSSSGGGGIIII____CCCCAAAAPPPPAAAACCCCIIIITTTTYYYY is set to the capacity of the root disk drive, in 512-byte blocks. The variables SSSSGGGGIIII____CCCCAAAAPPPP____ddddkkkkssss####dddd####vvvvoooollll are also set to correspond to the capacity of specific SCSI disk drives attached to the system. For example, if you have a 2 GB system disk (_d_k_s_0_d_1_v_o_l) and a 1 GB option disk (_d_k_s_0_d_2_v_o_l) then the following variables would be set: _SSSS_GGGG_IIII______CCCC_AAAA_PPPP_AAAA_CCCC_IIII_TTTT_YYYY_====_4444_1111_9999_7777_4444_0000_5555 _SSSS_GGGG_IIII______CCCC_AAAA_PPPP______dddd_kkkk_ssss_0000_dddd_1111_vvvv_oooo_llll_====_4444_1111_9999_7777_4444_0000_5555 _SSSS_GGGG_IIII______CCCC_AAAA_PPPP______dddd_kkkk_ssss_0000_dddd_2222_vvvv_oooo_llll_====_2222_0000_7777_0000_2222_3333_5555 SSSSGGGGIIII____RRRROOOOOOOOTTTT Set to the pathname of the directory where the actual system root directory (when the system is booted normally) is mounted. If the installation is being performed in the miniroot SSSSGGGGIIII____RRRROOOOOOOOTTTT is set to /_r_o_o_t; in a live installation (_r_o_b_o_i_n_s_t -_L), SSSSGGGGIIII____RRRROOOOOOOOTTTT is normally set to /. SSSSGGGGIIII____SSSSYYYYSSSSTTTTEEEEMMMMPPPPAAAARRRRTTTT The device name of the swap partition that the miniroot is loaded onto. For example, ddddkkkkssss0000dddd1111ssss0000. In live mode (-L) this is the partition where the directory / is mounted. SSSSGGGGIIII____SSSSYYYYSSSSTTTTEEEEMMMMDDDDIIIISSSSKKKK This is the same as SGI_SYSTEMPART, without the final partition number. For example, ddddkkkkssss0000dddd1111. SSSSGGGGIIII____CCCCUUUUSSSSTTTTOOOOMMMM Set to the pathname of the directory to which your _m_r_c_o_n_f_i_g file, and any other custom files, are copied during the automatic installation process. In a miniroot installation, this is usually /_c_u_s_t_o_m; in a live installation, SSSSGGGGIIII____CCCCUUUUSSSSTTTTOOOOMMMM is set to the name of a temporary directory, such as /_t_m_p/_d._r_o_b_o_i_n_s_t._N_N_N_N_N (where _N_N_N_N_N is a unique number). SSSSGGGGIIII____HHHHOOOOSSSSTTTTNNNNAAAAMMMMEEEE Set to the _h_o_s_t_n_a_m_e(1) of the client machine, or a NULL string if the hostname has not been set. SSSSGGGGIIII____SSSSYYYYSSSSIIIIDDDD Set to the system identifier comprised of 12 hexadecimal characters, for example, 08:00:69:07:73:80. PPPPaaaaggggeeee 5555 rrrroooobbbbooooiiiinnnnsssstttt____ccccoooonnnnffffiiiigggg((((1111MMMM)))) rrrroooobbbbooooiiiinnnnsssstttt____ccccoooonnnnffffiiiigggg((((1111MMMM)))) SSSSGGGGIIII____MMMMEEEEMMMMSSSSIIIIZZZZEEEE Set to the amount of memory on the system in megabytes (MB), as reported by _h_i_n_v(1). SSSSGGGGIIII____BBBBOOOOOOOOTTTTSSSSEEEERRRRVVVVEEEERRRR SSSSGGGGIIII____BBBBOOOOOOOOTTTTDDDDIIIIRRRR SSSSGGGGIIII____BBBBOOOOOOOOTTTTSSSSEEEERRRRVVVVEEEERRRR is set to the name of the machine from which the miniroot was booted. SSSSGGGGIIII____BBBBOOOOOOOOTTTTDDDDIIIIRRRR is set to the name of the directory containing that miniroot. SSSSGGGGIIII____CCCCOOOONNNNFFFFIIIIGGGGSSSSEEEERRRRVVVVEEEERRRR SSSSGGGGIIII____CCCCOOOONNNNFFFFIIIIGGGGDDDDIIIIRRRR SSSSGGGGIIII____CCCCOOOONNNNFFFFIIIIGGGGSSSSEEEERRRRVVVVEEEERRRR is set to the name of the machine from which your custom files (_m_r_c_o_n_f_i_g, ._i_n_d_e_x, etc.) were copied. SSSSGGGGIIII____CCCCOOOONNNNFFFFIIIIGGGGDDDDIIIIRRRR is set to the name of the directory containing those files. PPPPaaaarrrrttttiiiittttiiiioooonnnniiiinnnngggg Use the ppppaaaarrrrttttiiiittttiiiioooonnnn keyword to specify disk partitioning, filesystems and mount points. The syntax for this keyword is: ppppaaaarrrrttttiiiittttiiiioooonnnn _d_e_v_i_c_e _s_i_z_e _t_y_p_e _n_a_m_e _m_o_u_n_t-_o_p_t_i_o_n_s ; _m_k_f_s-_o_p_t_i_o_n_s ; The _d_e_v_i_c_e, _s_i_z_e, and _t_y_p_e arguments are used as input to the _f_x -_s command to perform disk partitioning. Partitions are laid out in the order specified, unless a start position is given. The _n_a_m_e and _m_o_u_n_t- _o_p_t_i_o_n_s (if any) are used as input to the _m_o_u_n_t(1M) command. The _m_k_f_s- _o_p_t_i_o_n_s (if any) are used as input to the _m_k_f_s__x_f_s(1M) command. For example to create a standard system disk layout one might use: partition dks0d1s0 standard root / or partition systemdisk standard root / And to create a standard option disk mounted at /d2: partition dks0d2s0 standard option /d2 NNNNooootttteeee:::: in order for repartitioning of the system disk to work properly, the ddddiiiisssskkkksssseeeettttuuuupppp keyword (described above) must appear in the _m_r_c_o_n_f_i_g file, or the ddddiiiisssskkkksssseeeettttuuuupppp====ttttrrrruuuueeee argument should be specified on the bbbbooooooootttt command line when initiating _r_o_b_o_i_n_s_t(_1_M) from the PROM command monitor. The partition arguments are as follows. _d_e_v_i_c_e is one of: ssssyyyysssstttteeeemmmmddddiiiisssskkkk a shorthand notation for partition 0 of the disk on which the miniroot is currently loaded (the current system disk). If this keyword is immediately PPPPaaaaggggeeee 6666 rrrroooobbbbooooiiiinnnnsssstttt____ccccoooonnnnffffiiiigggg((((1111MMMM)))) rrrroooobbbbooooiiiinnnnsssstttt____ccccoooonnnnffffiiiigggg((((1111MMMM)))) followed by a number (eg. ssssyyyysssstttteeeemmmmddddiiiisssskkkk1111) it refers to a specific partition on the system disk. _d_e_v_i_c_e _n_a_m_e The name of a disk device in the /_d_e_v/_r_d_s_k directory, for example ddddkkkkssss0000dddd1111ssss0000. See _d_k_s(7M) for a full description of device names. _s_i_z_e is one of: eeeexxxxiiiissssttttiiiinnnngggg Keep the same size. ssssttttaaaannnnddddaaaarrrrdddd Use a standard layout for the entire disk. Type rrrrooooooootttt or ooooppppttttiiiioooonnnn must also be specified (see below). When ssssttttaaaannnnddddaaaarrrrdddd is used, it applies to the entire disk (the _p_a_r_t_i_t_i_o_n component in the device name is irrelevant). For most partitioning tasks, either ssssttttaaaannnnddddaaaarrrrdddd rrrrooooooootttt or ssssttttaaaannnnddddaaaarrrrdddd ooooppppttttiiiioooonnnn should be specified as the first ppppaaaarrrrttttiiiittttiiiioooonnnn statement for the given disk. If customizations are desired, additional ppppaaaarrrrttttiiiittttiiiioooonnnn statements for that disk may also be specified. aaaallllllll The entire disk. _s_t_a_r_t:_s_i_z_e _s_t_a_r_t is an integer that specifies the exact start address of the partition, in 512-byte blocks. Alternatively, _s_t_a_r_t can be ffffoooolllllllloooowwwwssssppppaaaarrrrtttt#### where #### is the partition number which this partition is to immediately follow on the same disk. NNNNooootttteeee:::: the volume header is partition 8, so normally the first usable partition would use ffffoooolllllllloooowwwwssssppppaaaarrrrtttt8888. _s_i_z_e is an integer that specifies the size of the partition in 512-byte blocks, or the word rrrreeeemmmmaaaaiiiinnnnddddeeeerrrr to use the entire remainder of disk after making all other partitions. NNNNooootttteeee:::: partitions are processed in the order they appear in the file, so rrrreeeemmmmaaaaiiiinnnnddddeeeerrrr should be used only in the last ppppaaaarrrrttttiiiittttiiiioooonnnn statement for a particular disk. _t_y_p_e is one of: rrrrooooooootttt Only valid when ssssttttaaaannnnddddaaaarrrrdddd is specified (see above). A standard root disk is created, consisting of a swap partition and a root partition of maximum size containing an XFS filesystem. ooooppppttttiiiioooonnnn Only valid when ssssttttaaaannnnddddaaaarrrrdddd is specified (see above). A standard option disk is created, consisting of a single partition of maximum size, containing an XFS filesystem. PPPPaaaaggggeeee 7777 rrrroooobbbbooooiiiinnnnsssstttt____ccccoooonnnnffffiiiigggg((((1111MMMM)))) rrrroooobbbbooooiiiinnnnsssstttt____ccccoooonnnnffffiiiigggg((((1111MMMM)))) xxxxffffssss xxxxffffssss ////bbbblllloooocccckkkkssssiiiizzzzeeee An XFS filesystem is created with the specified _b_l_o_c_k_s_i_z_e, and mounted at the directory _n_a_m_e with the specified _o_p_t_i_o_n_s. The blocksize must be an integer multiple of 512 and cannot exceed 65536. If omitted, a blocksize of 4096 is assumed. eeeeffffssss An EFS filesystem is created, and mounted at the directory _n_a_m_e with the specified _o_p_t_i_o_n_s. CCCCaaaauuuuttttiiiioooonnnn:::: EFS filesystems will not be supported in future IRIX releases. Use XFS filesystems in nearly all situations. sssswwwwaaaapppp A swap partition of the specified _s_i_z_e is created. pppprrrreeeesssseeeerrrrvvvveeee Any existing filesystem is preserved, and no new one is created. _n_a_m_e is ignored when type is sssswwwwaaaapppp. For other partition types, its value can be: _p_a_t_h_n_a_m_e A local directory where the filesystem is to be mounted. nnnnoooommmmoooouuuunnnntttt If nnnnoooommmmoooouuuunnnntttt is specified, the filesystem is not mounted. _o_p_t_i_o_n_s are: ooooppppttttiiiioooonnnnssss See _m_o_u_n_t(1M) for legal options. This field is optional. Any ooooppppttttiiiioooonnnnssss specified are to be passed along to the _mmmm_oooo_uuuu_nnnn_tttt _----_oooo command as a single argument. Multiple options should be comma separated with no spaces. EEEExxxxaaaammmmpppplllleeee Consider the job of partitioning a set of Indy, O2/R5K and O2/R10K clients. The O2/R10K machines normally have the root drive at _d_k_s_0_d_2_s_0, but on the other we would like to use _d_k_s_0_d_1_s_0 for the root drive. This can be handled with a single _m_r_c_o_n_f_i_g file using the ssssyyyysssstttteeeemmmmddddiiiisssskkkk keyword as follows: # The following "disksetup" keyword applies to all machines disksetup partition systemdisk standard root / The same task could also be accomplished using explicit disk device names with: PPPPaaaaggggeeee 8888 rrrroooobbbbooooiiiinnnnsssstttt____ccccoooonnnnffffiiiigggg((((1111MMMM)))) rrrroooobbbbooooiiiinnnnsssstttt____ccccoooonnnnffffiiiigggg((((1111MMMM)))) # The following "disksetup" keyword applies to all machines disksetup if [ "$SGI_CPUBOARD" = IP32 -a "$SGI_CPUARCH" = R10000 ] then # On O2/R10K machines use drive 2 init echo This is an O2/R10K partition dks0d2s0 standard root / else # On my other machines put root on drive 1 init echo The machine type is $SGI_MACHINE partition dks0d1s0 standard root / endif For more examples, install the optional subsystem roboinst.sw.examples using _i_n_s_t(1M) or _S_o_f_t_w_a_r_e _M_a_n_a_g_e_r(1M). OOOOPPPPTTTTIIIIOOOONNNNSSSS The _r_o_b_o_i_n_s_t__c_o_n_f_i_g command accepts the following options: ----cccc _c_o_n_f_i_g_d_i_r Specify an alternate _r_o_b_o_i_n_s_t configuration directory. If no alternate configuration directory is specified, it is assumed to be the current directory. ----nnnn Do not write the table of contents. ----yyyy Always write the table of contents, even if it already exists. ----xxxx Do not write file size and checksum information to the table of contents. This option may be useful while debugging the _m_r_c_o_n_f_i_g file and other scripts in the configuration directory. However, if the table of contents does not contain file size and checksum information then it will not be possible to detect file transfer errors during the automatic installation process. FFFFIIIILLLLEEEESSSS _c_o_n_f_i_g_d_i_r/.index Table of contents for the specified configuration directory. /_u_s_r/_s_h_a_r_e/_s_r_c/_R_o_b_o_I_n_s_t/* RoboInst examples. SSSSEEEEEEEE AAAALLLLSSSSOOOO ABI(5), autoconfig(1M), dks(7M), fx(1M), hinv(1), hostname(1), inst(1M), mount(1M), nvram(1M), prom(1M), roboinst(1M), sh(1) and the online book _I_R_I_X _A_d_m_i_n: _S_o_f_t_w_a_r_e _I_n_s_t_a_l_l_a_t_i_o_n _a_n_d _L_i_c_e_n_s_i_n_g. PPPPaaaaggggeeee 9999 
